[18.0][MIG] uom_category_active: Migration to version 18.0#2221
Open
[18.0][MIG] uom_category_active: Migration to version 18.0#2221
Conversation
Member
|
@takahii03 Thanks for the migration! Commit history must be preserved. Can you please follow the steps described in https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#technical-method-to-migrate-a-module-from-170-to-180-branch? |
Currently translated at 100.0% (3 of 3 strings) Translation: product-attribute-16.0/product-attribute-16.0-uom_category_active Translate-URL: https://translation.odoo-community.org/projects/product-attribute-16-0/product-attribute-16-0-uom_category_active/it/
…se an error. Swith from an onchange logic to an create / write logic to be sure to handle all the cases
4e2c612 to
023b9db
Compare
Member
Author
|
@yostashiro |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, all.
The changes are mostly standard migration steps, with the exception of renaming a test class name to better align with current naming conventions.
Everything else followed the usual migration process.
Could you could take a look @angelmoya ?